Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 573-tree-1
name: 1499
tree-preservation-order: undefined
573-tpo-1
uprn
address-text
point: POINT (-0.971535 50.866790)
geometry: MULTIPOLYGON (((-0.971478 50.866784,-0.971481 50.866795,-0.971488 50.866805,-0.971501 50.866813,-0.971516 50.866818,-0.971534 50.866820,-0.971552 50.866819,-0.971568 50.866814,-0.971580 50.866806,-0.971589 50.866796,-0.971592 50.866785,-0.971589 50.866774,-0.971581 50.866764,-0.971569 50.866756,-0.971553 50.866750,-0.971536 50.866748,-0.971518 50.866750,-0.971502 50.866755,-0.971489 50.866763,-0.971481 50.866773,-0.971478 50.866784)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL